home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
swmeter
/
lock.exe
/
pak
/
LOCKER.DOC
next >
Wrap
Text File
|
1993-03-28
|
6KB
|
129 lines
---------------------------------------------------------------------
LOCKER.EXE Quickstart Manual Ver 1.20
Copyright (C) 1993 - AccuSys Computer Services ALL RIGHTS RESERVED
---------------------------------------------------------------------
Licence limit enforcement is becoming a major concern to public and
private corporations and organizations alike. The problem with most
commercial or shareware usage tracking programs is that they perform
their functions using some pretty elaborate methods, for example:
a. Database tracking - A database is created and hold all lock data
This can be really sloppy, not only must a database engine be
operating (and taking up memory) to maintain this database
but doing so may gobble up valuable system resources like
file handles and cache memory. Also, if the database corrupts
unexpectedly you may be faced with having to re-key all your
licence information. Should you wish to change metering programs
at a later date you can almost bet that the databases won't be
compatible.
b. Executable modification - The program is modified to add a
special pre-load header which checks the lock information before
running.
A potentially dangerous option. These type of programs directly
change your operational executable programs. Some programs may
not like this type of hacking and may simply stop. If you operate
any kind of virus scanner that checks for program modification
you can expect it to tilt when it finds that a program has been
modified by your locking program. Also, should the pre-load header
consult a database for it's information, than you can add the
above disadvantages to this option as well.
c. TSR - A resident program that sits around checking licences every
time a program is executed.
This is the ultimate ugly solution. Many of your users a tight on
memory as it is without throwing yet MORE junk in there. TSR's are
notorious for causing compatibility problems with both applications
and systems software. TSR's may also hold files open on the server
thereby reducing the available file handles for other applications.
The LOCKER.EXE alternative:
a. NO DATABASES to hog system resources or corrupt unexpectedly and
hang your whole system
b. NO OPEN FILES to reduce system resources
c. NO PROGRAM MODIFICATIONS that may crash a program or tilt a virus
scanning program.
d. NO TSR's chewing up your precious memory
Locker runs, checks lock status and exits. All files opened (only 2) are
released immediately when the program terminates.
If you need additional help with this program, please call 416-734-1992 or
for more direct assistance, please EMAIL compuserve address 71753,3522
Step 1.
Create a directory on a shared Netware drive which is to hold the
lock files. Users must be able to Filescan, Read, Create, and Erase
files in this directory.
Step 2.
Establish handy abbreviations, I suggest 5 characters maximum, to
be used to identify your applications (eg. WP51 for WordPerfect 5.1)
This abbreviations will be used to create the USERLOCK.DAT file
Step 3.
Using your favorite text editor (such as Edit, Edlin...etc) and create
a file called USERLOCK.DAT in the directory created in step 1.
Each line of the file has the same pattern:
APPL_ABBREVIATION LICENCE_LIMIT
The abbreviation is separated from the licence limit by whitespace
(spaces, tabs, etc...) If LOCKER is called and the specified
abbreviation cannot be found in USERLOCK.DAT the program will assume
a single user (1 user) licence and create a ???.001 file for the
requested application. This means that you only have to make
entries for those programs with a multi-user licence.
A sample USERLOCK.DAT is included on the diskette. After you have
prepared your USERLOCK.DAT file, I would suggest FLAGing the file
Shareable, Read-Only. This will prevent users from deleting the file
if permissions were assigned as indicated above in step 1. Netware
3.11 users can use the Trustee File Permissions to grant Modify rights
to any users who must maintain the USERLOCK.DAT file.
NOTE: Some of the sample applications use high licence limits. If you
are running the DEMO version of LOCKER these limits are
automatically reduced to 10 by the program.
Step 4.
Create batch files to run your applications. Note that locker will
return a positive number (the lock file number) if successful. This
facility was provided for users who might want to use the lock file
number in a batch file. On failure to lock the program will return
zero (0). A sample batch file might look like this:
@ECHO OFF
LOCK F:\APPS\LOCKS LOCK WP51
IF ERRORLEVEL 1 GOTO CONTINUE
ECHO Sorry, all licences are in use. Please try again later.
GOTO END
:CONTINUE
WP51
LOCK F:\APPS\LOCKS UNLOCK WP51
IF ERRORLEVEL 1 GOTO END
ECHO Error unlock file, please advise LAN administrator.
:END
Step 5.
I would suggest that you create some automated procedure for viewing
and cleaning LOCK files. Should a user reboot without exiting the
application, a lock file will be left behind and will remain stranded
until it is removed. Lock files contain a viewable plain text header
which can be examined with the DOS "TYPE" command. To remove an
errant lock file simply delete it from the directory.